Browser autofill can dispatch synthetic keyboard events where modifier keys
(altKey, ctrlKey, etc.) have undefined values instead of booleans. This
causes WASM binding errors when the undefined values are passed to Rust.

Added serde(default) attributes to all modifier key fields in
SerializedKeyboardData to gracefully handle undefined values by defaulting
them to false.

This fixes the 'expected a boolean argument, found undefined' errors that
occur during browser autofill scenarios.

Browser autofill can send keyboard, mouse, touch, and pointer events with
undefined modifier key properties (altKey, ctrlKey, metaKey, shiftKey).
This causes wasm-bindgen to throw "expected a boolean argument, found undefined"
errors when these events are serialized.

Added null coalescing operators (?? false) to all event serialization functions
to ensure modifier keys default to false when undefined.

Fixes browser autofill crashes in WASM applications.

Compiled TypeScript files to JavaScript using Bun after adding null
coalescing operators to handle undefined modifier keys in event serialization.

This completes the fix for browser autofill crashes by ensuring both the
Rust serde side and JavaScript serialization side handle undefined
modifier keys properly.

Browser autofill can send events with undefined modifier key properties
(altKey, ctrlKey, metaKey, shiftKey) and undefined string properties
(key, code). This causes wasm-bindgen to throw type assertion errors.

Added defensive property access using wasm_bindgen::JsValue conversion
with appropriate defaults:
- Boolean modifier keys default to false when undefined
- String properties default to "Unidentified" when undefined

This prevents "expected a boolean argument, found undefined" and
"expected a string argument, found undefined" errors during browser
autofill events.

Fixed in all event types that access modifier keys:
- KeyboardEvent, MouseEvent, WheelEvent, TouchEvent, DragEvent, PointerEvent

Added defensive null coalescing for KeyboardEvent key and code properties
in the TypeScript serialization layer. Browser autofill can send undefined
values for these properties, which was causing wasm-bindgen assertion errors.

Additional fixes for handling undefined properties in browser autofill events.

…erializeEvent`

…rsions

- Add Default implementations for all event data types to handle browser autofill crashes gracefully
- Use specific ClipboardEvent type instead of generic Event for consistency
- Remove general unchecked_convert macro that was creating unnecessary unsafe conversions
- Keep safe conversions using dyn_into with fallback to default values
- Improve type consistency across all event converters

This ensures the browser autofill crash is properly handled while making the codebase safer by removing unnecessary unchecked type conversions.